Offline upgrade

Use this procedure to perform an offline upgrade to Power Operation 2024 R1.

Perform the offline upgrade process in a test environment and before traveling to the production site. Doing this will identify potential conflicts in the upgrade process that can be fixed before attempting an online upgrade. This will minimize server downtime in the online upgrade process or save time and effort if completing an offline upgrade in the Production environment.

  1. Backup your current project and other relevant files from all servers in the system:
    File to back upDescription

    Project backup (.ctz file)

    This is the main file to back up. For information about backing up a project, refer to your current version's online help. You need to have the Save sub-directories and Save configuration files options selected in the Backup dialog.

    Citect.ini

    This file is in the config folder.

    Deployment configuration filesIf you have deployment configured, back up the following files:
    • SE.Asb.Deployment.Server.WindowsService.exe.config
    • SE.Asb.Deployment.Node.WindowsService.exe.config.
    These are in the path [CtEdit]Config.

    Data directory

    This file is found on the path [CtEdit]Data

    Deployment databaseThis is in the Deployment directory. For example: %PROGRAMDATA%\AVEVA Plant SCADA 2023 R2\Deploy
    PostgreSQL data directory

    This is required if you want to use the existing data from your current PostgreSQL database in the new installation of EPO. Data directory can be found here:

    .. \ProgramData\Schneider Electric\Power Operation\v2022(previous version)\database

    ALMSAV.DAT and ALMINDEXSAVE.DAT (For v7.20)

    OR

    Alarm Database (for v7.30SR or later)

    <ProjectName>_<ClusterName>_ALMSAV.DAT and <ProjectName>_<ClusterName>_ALMINDEXSAVE.DAT. These files contain alarm configuration data and runtime data. Their path is defined in the Citect.INI file. The default path is same as the data directory path.

    The Alarm Database is located in the Data directory: [Data]\<Project Name>\<ClusterName.AlarmServerName>. For each alarm server you have in your system, a corresponding Alarm Database will exist. You need to back up all alarm databases.

    Trend files: *.HST and *.00X

    The path and names of these files are defined on the trend tag itself and created in the Data directory defined in [CtEdit]Data. The files will be named after the trend name and number of files. For example, if the trend name is CPU, file names will be CPU.HST, CPU.001, CPU.002, etc..

    Report Files

    These files contain the code that is executed on your reports, and are in the [CtEdit]User\<Project Name> folder.

    Custom ActiveX Controls (.OCX)

    Power Operation includes some ActiveX controls, which are available with this version, but you need to take a backup of your custom ActiveX controls.

    Check your ActiveX.dbf file in the [CtEdit]User\<Project Name> folder. This file contains a list of the ActiveX controls in your project and their GUID. Using the GUID, find the path of an ActiveX control using the Windows Registry key:

    KEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\"GUID"\InProcServer32\.

    The default value for this key is a path to the .DLL or .OCX file you need to back up.

    Process Analyst filesBackup the main <Project Folder>\Analyst Views and <Project Folder>\Dictionary folders.

    Device logs

    These files contain any logging (alarm logs, report logs) you have configured in your project. You will find their location in the Devices dialog.

    Additional Files

    Check your Citect.ini file or use the Setup Editor | Paths section as it could contain runtime files used by custom code in the project.

    It is also recommended to search C:\ or other volumes where multiple hard disks are installed, in the Power Operation Studio > Find and Replace tool. These search results will display any paths in use by all project components.

    Web Applications

    If you have made any manual updates and edits, other than machine-name edits, you will need to manually back up and restore web files.

    For the following destination files, manually merge edits, rather than overwriting:

    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Services\Platform Server\appsettings.json
    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Services\Pso WebService\appsettings.json
    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Web\WebHmi\web.config
    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\AppServices\bin\Configuration.xml

    Restore the following files by overwriting:

    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Web\SystemDataService\App_Data\Configuration\ApplicationMenuConfig.json
    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Web\SystemDataService\App_Data\Configuration\HmiConfiguration.json
    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Web\SystemDataService\App_Data\Configuration\CustomScript\DeployJS\*.*
    • C:\Program Files (x86)\Schneider Electric\Power Operation\v2021\Applications\Services\Platform Server\classifications.json

    NOTE: Recreate Alarm views and Trend views manually.

    Driver Hotfixes

    If you are aware of any driver hotfix in your system, back up this driver DLL, located in the Bin directory where Power Operation is installed.

    NOTE: The fixes contained in this hotfix might be included in the drivers which ship with this version.

    Go to the Power Operation Schneider Electric Exchange for additional driver downloads or Citect Driver Web for additional driver downloads.

  2. Upgrade your licenses.

    Have a valid support agreement, or purchase an upgrade license, and upgrade your key or soft license using the online license generator.

    If your license is out of support, contact your Schneider Electric account manager or email orders.software@se.com with your license and site ID details.

  3. Uninstall the current version and install the latest version and proceed with upgrading and migrating the project configuration for later use in the production environment. See Upgrade path for details on upgrade requirements based on version.

    • If upgrading in a production environment as part of an Offline or Online upgrade process: Uninstall the current version of Power Operation and install the next version specified in your upgrade path.

    • If this is step is done in a test environment: It is unnecessary to install the next software version in the upgrade path. Upgrade directly. Go to the Power Operation Schneider Electric Exchange for downloads.

  4. Install Power Operation 2024.
  5. If required, configure EPO to use data from curent installation of PostgreSQL database.
  6. (Optional) Configure EPO to use the new version of PostgreSQL database.
  7. Configure the Server Password using the Computer Setup Wizard. See Power Operation Server password.

  8. Configure the System Management Server: In the Plant SCADA help search box, type Configure a System Management Server and click the search icon.

  9. Restore your project and select all included projects if available. PLS_Include will be restored.
  10. Upgrade your project.

    • As a default, when you restore your project from a previous version, Power Operation will force an update, and you will get a warning message. Click Yes to proceed with project upgrade. If this message is not displayed, you can force an update of all projects by setting the [CtEdit]Upgrade INI parameter to 1 and restarting Power Operation. After you restart, you will get a warning message.

    • Pack all projects in the Power Operation Studio > Projects screen and Pack Libraries in Active and Included projects in the Graphics Builder > Tools menu.

  11. Migrate your project.

    The automatic project upgrade does not fully upgrade your projects, and needs to be followed by the Migration tool. The Citect and Power Operation Migration Tools are separate applications that must be run manually after the project upgrade has been executed, and adds computers from the existing topology. You might need to run the Citect Migration tool separately for other components. Refer to the online help for more information about running the Citect Migration tool.

    • Run the Citect and Power Operation Migration Tools.

    • Confirm that all IO devices in the project have been assigned Equipment names.

  12. Merge your .INI file.

    • In addition to the INI settings below, identify other custom INI settings that might be required for the proper operation of the upgraded software project. The Computer Setup Editor tool is especially useful for comparing the old and new INI files. Select "Compare INI Files" from the Computer Setup Editor > Tools menu.

    • When upgrading a standby server, first merge the standby server's existing .INI into the upgraded version .INI. Then compare this result to the upgraded, merged .INI from the primary server to confirm they are consistent; the two files should have consistent [Alarm], [Trend], [Report] and driver parameters. Other parameters that include <Server>, <Cluster> or <Device> names will have different parameter names but similar values.

    • If you have defined the following parameters in your Citect.INI file, merge them into the new version's INI file:

    ParameterDescription

    [General]

    TagStartDigit=1

    Without this parameter, you will encounter the Tag not defined compiler error. Setting this to 1 lets you define tag names that begin with a number or a symbol.

    [General]

    CheckAddressBoundary=0

    Without this parameter, you could encounter the 'Bad Raw Data' or other tag address related errors. Setting this to 0 allows defining variable tags of the same data type in odd or even addresses. When this parameter is set to 1 all variable tags from the same data type need to be defined on odd OR even addresses.

    [General]

    ClusterReplication=1

    		Without this parameter, compile will fail in a multi-cluster system. Setting this parameter to 1 will enable tag/tag reference replication in a multi-cluster system.

    [CtDraw.RSC]

    ListSystemPage=1

    This lets you open popup pages from Graphics Builder.

    [CtDraw.RSC]

    AllowEditSuperGeniePage=1

    This lets you edit super genie pages from Graphics Builder.

    [CtEdit]

    DbFiles=100

    		This lets you set the maximum number of .DBF files that can open simultaneously. Allowable values are between 50 to 32767 with the default set to 100. Increase the value of this parameter for larger projects.

    Merge any driver parameters from your old .INI file as they will most likely be necessary to interface with your I/O network. For a list of changes to .INI parameters, see Upgrade references.

  13. Compile your project.

    After upgrading your project and running the Migration tool, compile your project to ascertain that runtime functionality works as expected. It is likely that you will encounter errors when you compile your project. One of the most common sources of errors when upgrading is Cicode functions. This is because functions changed, were deprecated, or because the compiler code has been updated to prevent runtime errors.

    After fixing any errors, do the following:

    1. Use the Power Operation Studio > Options menu to deselect Incremental Compile.
    2. Pack the project from Power Operation Studio > Projects screen.
    3. Update Pages and Pack Libraries in the Active/Include projects from the Graphics Builder.
    4. Compile the project again.
  14. Run the Setup Wizard.

    Before running your project, run the Setup Wizard (known as Computer Setup Wizard in previous versions) to configure the Runtime Manager and other settings that are relevant to the runtime process. The Setup Wizard will automatically determine the role of your computer based on the network addresses defined in your project. After finishing the Setup Wizard, restore your historic data and other files, and run your project.

    Be sure to enter the Server Password obtained or created before the upgrade on the Server Authentication screen of the wizard. See Online upgrade for prerequsites.

  15. Restore and merge the backed up web application files described in the table previous.
  16. Restore runtime files.

    After compiling your project, place the files necessary for runtime in the correct directories. Refer to step one in this topic for the list of files you need to place in the corresponding directories as defined in your Citect.INI file and project configuration.

  17. Restore historical data files (necessary if upgrading in the production environment).

    Restore the historical data files before running your upgraded projects. It is not required to restore these files when performing the Online upgrade or if upgrading the project in a test environment. During an Online upgrade these files will be restored automatically through Primary-Standby server synchronization.

    NOTE: Consideration should be given to the size of the alarm and trend files. Automatic Primary-Standby server synchronization can take a long time, depending on the size of these files.

    Alarms (v7.20 SR1 and earlier)

    Before you can upgrade to Power Operation 2024, perform the following steps to convert your <Project Name>_<Cluster Name>_ALMSAV.DAT and <Project Name>_<Cluster Name>_ALMINDEXSAVE.DAT files to a format that can be read by the new alarm server architecture introduced in v7.30:

    Make sure that the [Alarm]SavePrimary parameter points to the directory in which you have placed your backed-up ALMSAV.DAT and ALMINDEXSAVE.DAT

    For Alarms in v2020, v2020 R2, v9.0, v7.30SR1, v7.40, v7.40 SR1, v8.0, v8.0 SR1 and v8.1, convert your Alarm Database in the Data directory:

    1. Confirm your backed-up Alarm Database is in the directory defined by the [CtEdit]Data parameter.
    2. Before starting runtime, confirm that the directory [Alarm]SavePrimary does NOT contain ANY ALMSAV.DAT nor ALMINDEXSAVE.DAT files.
  18. Stop and restart the Schneider Electric CoreServiceHost service using the Windows Services management console. Execute the iisreset command using the Windows Command Prompt.
  19. Follow these steps to convert the files:
    1. Create the same file hierarchy on the new system.
    2. Place the files in the same folders.
    3. If you want to change the folder location, or you cannot replicate the same file hierarchy, use the trend renaming tool available on the Schneider Electric Exchange.
  20. Run your project.

    Run your project to check that the functionality works as intended:

    • Check any Cicode that you needed to modify to compile your project.
    • Test communications to your I/O devices, alarm triggering, and trend capture.
  21. Update settings in the Application Config Utility.

    The authentication settings in the Citect Data Platform and settings of the One-Line Engine screens need to be completed. Confirm that your redundancy parameters are set for the one-line engine in a redundant system.

  22. (Optional) Add Upgrade options in Upgrading to the project, recompile, and test.

NOTE: If upgrading from v9.0 or earlier, decommission legacy web clients and web servers. For more information on decommissioning, see Decommissioning procedures.